Fibre channel switch system

ABSTRACT

A Fibre Channel (FC) switch system includes a server IHS and a storage IHS that each communicate using an FC protocol. A switch IHS couples the server IHS to the storage IHS. A first converter in the switch IHS receives first FC data traffic from the server IHS and converts it to first FC over Ethernet (FCoE) data traffic. A protocol processing engine in the switch IHS is coupled to the first converter and receives the first FCoE data traffic from the first converter and processes it to provide second FCoE data traffic for delivery to the storage IHS. A second converter in the switch IHS is coupled to the protocol processing engine and the storage IHS and receives the second FCoE data traffic from the protocol processing engine, converts it to second FC data traffic, and sends the second FC data traffic to the storage IHS.

BACKGROUND

The present disclosure relates generally to information handlingsystems, and more particularly to a Fibre Channel switch system forinformation handling systems.

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system (IHS). An IHS generallyprocesses, compiles, stores, and/or communicates information or data forbusiness, personal, or other purposes. Because technology andinformation handling needs and requirements may vary between differentapplications, IHSs may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in IHSs allowfor IHSs to be general or configured for a specific user or specific usesuch as financial transaction processing, airline reservations,enterprise data storage, or global communications. In addition, IHSs mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Some IHSs include storage area networks (SANs) that provide a pluralityof storage IHSs that communicate with server IHSs to provide storage ofinformation for the server IHSs. In many cases, those SANs are connectedto the server IHSs using a Fibre Channel (FC) fabric that is currentlythe core component of most SANs. That FC fabric is enabled using FCswitch IHSs that incorporate expensive and proprietary FC switch chipsand FC software stacks. Those expensive and proprietary FC switch chipsand FC software stacks require relatively large upfront investments thathave provided a barrier to entry to the FC market that has resulted in aconsolidation of the FC market, and impeded the adoptions of SANs.

Accordingly, it would be desirable to provide an improved FC switchsystem.

SUMMARY

According to one embodiment, a Fibre Channel (FC) switch system includesa first converter that is coupled to a first port and that is configuredto receive first FC data traffic from an initiator system through thefirst port and convert the first FC data traffic to first FC overEthernet (FCoE) data traffic; a protocol processing engine that iscoupled to the first converter and that is configured to receive thefirst FCoE data traffic from the first converter and process the firstFCoE data traffic to provide second FCoE data traffic for delivery to atarget system; and a second converter that is coupled to the protocolprocessing engine and a second port, wherein the second converter isconfigured to receive the second FCoE data traffic from the protocolprocessing engine, convert the second FCoE data traffic to second FCdata traffic, and send the second FC data traffic through the secondport to the target system.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic view illustrating an embodiment of an informationhandling system.

FIG. 2 is a schematic view illustrating an embodiment of a Fibre Channel(FC) switch system.

FIG. 3 a is a flow chart illustrating an embodiment of a portion of amethod for storage/switch set-up in the FC switch system of FIG. 2.

FIG. 3 b is a flow chart illustrating an embodiment of a portion of amethod for storage/switch set-up in the FC switch system of FIG. 2.

FIG. 4 a is a flow chart illustrating an embodiment of a portion of amethod for server/switch set-up in the FC switch system of FIG. 2.

FIG. 4 b is a flow chart illustrating an embodiment of a portion of amethod for server/switch set-up in the FC switch system of FIG. 2.

FIG. 5 is a flow chart illustrating an embodiment of a method forserver/storage communication via the switch in the FC switch system ofFIG. 2

DETAILED DESCRIPTION

For purposes of this disclosure, an IHS may include any instrumentalityor aggregate of instrumentalities operable to compute, classify,process, transmit, receive, retrieve, originate, switch, store, display,manifest, detect, record, reproduce, handle, or utilize any form ofinformation, intelligence, or data for business, scientific, control,entertainment, or other purposes. For example, an IHS may be a personalcomputer, a PDA, a consumer electronic device, a display device ormonitor, a network server or storage device, a switch router or othernetwork communication device, or any other suitable device and may varyin size, shape, performance, functionality, and price. The IHS mayinclude memory, one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic. Additionalcomponents of the IHS may include one or more storage devices, one ormore communications ports for communicating with external devices aswell as various input and output (I/O) devices, such as a keyboard, amouse, and a video display. The IHS may also include one or more busesoperable to transmit communications between the various hardwarecomponents.

In one embodiment, IHS 100, FIG. 1, includes a processor 102, which isconnected to a bus 104. Bus 104 serves as a connection between processor102 and other components of IHS 100. An input device 106 is coupled toprocessor 102 to provide input to processor 102. Examples of inputdevices may include keyboards, touchscreens, pointing devices such asmouses, trackballs, and trackpads, and/or a variety of other inputdevices known in the art. Programs and data are stored on a mass storagedevice 108, which is coupled to processor 102. Examples of mass storagedevices may include hard discs, optical disks, magneto-optical discs,solid-state storage devices, and/or a variety other mass storage devicesknown in the art. IHS 100 further includes a display 110, which iscoupled to processor 102 by a video controller 112. A system memory 114is coupled to processor 102 to provide the processor with fast storageto facilitate execution of computer programs by processor 102. Examplesof system memory may include random access memory (RAM) devices such asdynamic RAM (DRAM), synchronous DRAM (SDRAM), solid state memorydevices, and/or a variety of other memory devices known in the art. Inan embodiment, a chassis 116 houses some or all of the components of IHS100. It should be understood that other buses and intermediate circuitscan be deployed between the components described above and processor 102to facilitate interconnection between the components and the processor102.

Referring now to FIG. 2, an embodiment of a Fibre Channel (FC) switchsystem 200 is illustrated. The FC switch system 200 includes a switchIHS 202 which may be, for example, the IHS 100 discussed above withreference to FIG. 1, and/or which may include some or all of thecomponents of the IHS 100. The switch IHS 202 includes a protocolprocessing engine 204 that may be provided by a processing system, suchas the processor 102 discussed above with reference to FIG. 1, and amemory system, such as the system memory 114 discussed above withreference to FIG. 1. For example, the memory system may includeinstructions that, when executed by the processing system, cause theprocessing system to perform the functions of the protocol processingengine 204 discussed below. In an embodiment, the processing system thatprovides the protocol processing engine 204 includes an Ethernet switchchip such as, for example, an Ethernet switch Application SpecificIntegrated Circuit (ASIC), and a Central Processing Unit (CPU). While inthe embodiments discussed below, specific actions are discussed as beingperformed by the CPU and the Ethernet switch chip, in differentembodiments, the actions performed by the CPU may be performed by theEthernet switch chip or some other processing system (e.g., a processingsystem that performs the actions of both the CPU and the Ethernet switchchip) while remaining within the scope of the present disclosure. In anembodiment, the memory system that provides the protocol processingengine 204 may include Ethernet layer 2 (L2) forwarding tables.

As discussed above, conventional FC fabrics utilize FC switch IHSs thatinclude expensive and proprietary FC switch chips, and the FC switchsystem 200 of the present disclosure may provide at least a portion ofan FC fabric that includes the switch IHS 202 with an Ethernet switchchip that one of skill in the art will recognize is relativelyinexpensive compared to the FC switch chips discussed above based on thewidespread use of Ethernet switch chips in a variety of networkingapplications and the resulting economies of scale. In the embodimentsdiscussed in further detail below, the switch IHS 202 may provide forthe transmission of FC data traffic between server IHSs and storage IHSsutilizing an Ethernet switch chip, which operates via a different OpenSystem Interconnect (OSI) physical (PHY) layer than FC switch chipsincluded in conventional FC switch IHSs, and the converters and softwarestack discussed below. However, one of skill in the art in possession ofthe present disclosure will recognize how different processing systems,converters, and software stacks may enable other inexpensive chips toreplace the FC switch chips discussed above while remaining within thescope of the present disclosure. As discussed above, the processingsystem that provides the protocol processing engine 204 may also includea Central Processing Unit (CPU) that, for example, handles controlprotocols and configuration of the switch IHS 202 as discussed below,while the Ethernet switch chip performs data traffic processing andforwarding.

The FC switch system 200 includes a first converter 206 that mayinclude, for example, a PHY chip and a memory system that includesinstructions that, when executed by the PHY chip, cause the PHY chip toprovide an FC-to-FCoE engine 206 a, an FCoE-to-FC engine 206 b, and/orperform any of the other functions of the first converter 206 discussedbelow. As described below, the FC-to-FCoE engine 206 a and/or theFCoE-to-FC engine 206 b may operate as FC/FCoE encapsulator/decapsultorsat the PHY layer, providing an FC port-level state machine, framing, andPHY level FC/FCoE conversion. The FC switch system 200 also includes asecond converter 208 that may include, for example, a PHY chip and amemory system that includes instructions that, when executed by the PHYchip, cause the PHY chip to provide an FC-to-FCoE engine 208 a, anFCoE-to-FC engine 208 b, and/or perform any of the other functions ofthe second converter 208 discussed below. As described below, theFC-to-FCoE engine 208 a and/or the FCoE-to-FC engine 208 b may operateas FCoE/FC encapsulator/decapsultors at the PHY layer, providing an FCport-level state machine, framing, and PHY level FCoE/FC conversion. Thefirst converter 206 is coupled to a plurality of ports 210 on the switchIHS 202, and the second converter 208 is coupled to a plurality of ports212 on the switch IHS 202.

The FC switch system 200 also includes a server IHS 214. In anembodiment, the server IHS 214 may be, for example, the IHS 100discussed above with reference to FIG. 1, and/or may include some or allof the components of the IHS 100. In the illustrated embodiment, theserver IHS 214 includes an initiator Host Bus Adapter (HBA) 214 a thatis coupled to a first port 210 a of the plurality of ports 210 on theswitch IHS 202 using a cable or other coupling system known in the art.The FC switching system 200 also includes a storage IHS 216. In anembodiment, the storage IHS 216 may be, for example, the IHS 100discussed above with reference to FIG. 1, and/or may include some or allof the components of the IHS 100. In the illustrated embodiment, thestorage IHS 216 includes a target Host Bus Adapter (HBA) 216 a that iscoupled to a second port 212 a of the plurality of ports 212 on theswitch IHS 202 using a cable or other coupling system known in the art.One of skill in the art in possession of the present disclosure willrecognize that the use of “initiator” and “target” with reference to theHBAs 214 a and 216 a is provided for clarity of discussion with regardto the example of server/storage communications discussed below, anddifferent communication examples will fall within the scope of thepresent disclosure. As discussed below, each of the server IHS 214 andthe storage IHS 216 may include memory systems that include instructionsthat, when executed by processing systems in the server IHS 214 orstorage IHS 216, cause the processing systems to communicate using FCProtocols in order to, for example, transport Small Computer SystemInterface (SCSI) commands over a FC network (e.g., the FC fabricincluding the switch IHS 202) provided between them.

Referring now to FIGS. 3 a, 3 b, 4 a, 4 b, and 5, methods 300, 400, and500 are illustrated and described for providing an FC switch system.Specifically, an embodiment of a method 300 for providing storage/switchset-up in the FC switch system 200 is first described, a method 400 forproviding server/switch set-up in the FC switch system 200 is thendescribed, and then a method 500 for providing server/storagecommunication in the FC switch system 200 is described. The methods 300and 400 are discussed below as setting up and providing communicationbetween the single server IHS 214 and the single storage IHS 216 usingthe switch IHS 202, but communications between any number of server IHSsand storage IHSs may be set up in a similar manner, and one of skill inthe art in possession of the present disclosure will recognize that themethods 300 and 400 may be performed concurrently, may overlap, may beperformed in a reverse order relative to that presented herein, and/ormay be subject to other modifications while remaining within the scopeof the present disclosure and allowing for the method 500 to beperformed as discussed below. In the embodiments discussed below, theInitiator HBA 214 a and the Target HBA 216 a may be configured in acommon zone such that they may communicate, as would be understood byone of skill in the art.

Referring first to FIGS. 3 a and 3 b, the method 300 for providingstorage/switch set-up is illustrated. In an embodiment, the method 300may begin when the processing system of the switch IHS 202 first runs FCswitch code in a software stack that is stored in the memory system ofthe switch IHS 202 in response to, for example, connection, power up, orother initialization of the FC switching system 200. In someembodiments, during port initialization of the switch IHS 202 and priorto the method 300, the second converter 208 is programmed (e.g., byprogramming the PHY chip) to perform a formatted conversion of native FCtraffic (e.g., 8 Gb/s FC traffic) into formatted FC over Ethernet (FCoE)traffic (e.g., 10GE FCoE frames). For example, the second converter 208may be programmed to prepend a specific 3 byte FC-MAP (currently00:00:00) to all incoming FC traffic FCID's, producing a specific 10GEframe of format (currently 00:00:00:DD:AA:PP, where DD=domain (the firstbyte of the FCID), AA=area (the second byte of the FCID), and PP=port(the third byte of the FCID, also referred to as the Arbitrated LoopPhysical Address (ALPA))) for both source and destination addresses.

In some embodiments, during switch initialization of the switch IHS 202and prior to the method 300, FCoE formatted FC Well Known Addresses(WKA's) are registered in the second converter 208 as Ethernet bridgingprotocol addresses, which operates to direct incoming FC Well KnownAddress (WKA) traffic that has been converted to the formatted FCoEtraffic to be sent to the Ethernet switch chip such that it may behandled using the FC switch code that is executable by the CPU. Inaddition, standard Ethernet bridging protocol addresses (e.g., bridgingprotocol data units such as 01:80:c2:XX:XX:XX frames) may bederegistered from the Ethernet switch chip. For example, the cache inthe switch IHS 202 that includes standard Ethernet bridging protocoladdresses may be cleared, and in some cases the resulting defaultmulticast/broadcast addresses may be cleared as well, followed by theprovisioning of FC style entries in the cache of the switch IHS 202.Furthermore, the Ethernet switch may also be configured to not forwardbroadcast, multicast, or unknown unicast data traffic. As discussed inthe method 300 below, the FC switch code executable by the CPU handlesand generates protocol frames in the specific FCoE format discussedherein.

The method 300 begins at block 302 where the target HBA in the storageIHS sends an FC fabric login (FLOGI) to the switch IHS. In anembodiment, the target HBA 216 a in the storage IHS 216 generates andsends an FC FLOGI that may include the Login Server WKA 0xFFFFFE to thesecond port 212 a on the switch IHS 202. In an example, that FC FLOGImay include a System Identification (SID) (e.g., 00:00:00, an unassignedFC identification) and a Destination Identification (DID) (e.g.,FF:FF:FE, the Login Server WKA).

The method 300 then proceeds to block 304 where the second converterconverts the FC FLOGI to an FCoE FLOGI and provides the FCoE FLOGI tothe protocol processing engine. In an embodiment, the second converter208 receives the FC FLOGI through the second port 212 a and provides itto the FC-to-FCoE engine 208 a, which operates to convert the FC FLOGIto an FCoE FLOGI by wrapping the FC FLOGI in an FCoE header and trailer.In an example, the FCoE FLOGI may include a source media access control(SMAC) address (e.g., 00:00:00:00:02:00), a destination MAC (DMAC)address (e.g., 00:00:00:FF:FF:FE, a pre-programmed layer 2 (L2) cacheentry), a SID (e.g., 00:00:00) and a DID (e.g., FF:FF:FE). The secondconverter 208 sends that FCoE FLOGI to the protocol processing engine204. In an embodiment, the Ethernet switch chip in the protocolprocessing engine 204 receives the FCoE FLOGI and provides it to the CPUin the protocol processing engine 204.

The method 300 then proceeds to block 306 where the protocol processingengine sends an FCoE FLOGI accept (ACC) to the second converter. In anembodiment, the protocol processing engine 204 receives the FCoE FLOGIand, if the FCoE FLOGI is accepted, replies with an FCoE FLOGI ACC thatis sent to the second converter 208. In an embodiment, the CPU in theprotocol processing engine 204 determines whether the FCoE FLOGI isaccepted and, if so, sends an FCoE FLOGI ACC to the Ethernet switch chipin the protocol processing engine 204, which forwards the FCoE FLOGI ACCto the second converter 208. Processing actions to determine whether anFCoE FLOGI is accepted are known in the art and not discussed in furtherdetail here. In an example, an FCoE FLOGI ACC may include an SMACaddress (e.g., 00:00:00:FF:FF:FE), a DMAC address (e.g.,00:00:00:03:02:00), a SID (e.g. FF:FF:FE), and a DID (e.g., 03:02:00).

The method 300 then proceeds to block 308 where the second converterconverts the FCoE FLOGI ACC to an FC FLOGI ACC and provides the FC FLOGIACC to the target HBA in the storage IHS. In an embodiment, the secondconverter 208 receives the FCoE FLOGI ACC from the protocol processingengine 204 and provides it to the FCoE-to-FC engine 208 b, whichoperates to convert the FCoE FLOGI ACC to an FC FLOGI ACC by strippingthe FCoE header and trailer from the FCoE FLOGI ACC. In an example, theFC FLOGI ACC includes a SID (e.g., FF:FF:FE) and a DID (e.g., 03:02:00).The second converter 208 sends that FC FLOGI ACC through the second port212 a to the target HBA 216 a in the storage IHS 216.

The method 300 then proceeds to block 310 where the target HBA in thestorage IHS sends an FC port login (PLOGI) to the switch IHS. In anembodiment, in response to receiving the FC FLOGI ACC, the target HBA216 a in the storage IHS 216 generates and sends an FC PLOGI that mayinclude the Name Server WKA 0xFFFFFC to the second port 212 a on theswitch IHS 202. In an example, the FC PLOGI includes a SID (e.g.,03:02:00) and a DID (e.g., FF:FF:FC, the Name Server WKA).

The method 300 then proceeds to block 312 where the second converterconverts the FC PLOGI to an FCoE PLOGI and provides the FCoE PLOGI tothe protocol processing engine. In an embodiment, the second converter208 receives the FC PLOGI through the second port 212 a and provides itto the FC-to-FCoE engine 208 a, which operates to convert the FC PLOGIto an FCoE PLOGI by wrapping the FC PLOGI in an FCoE header and trailer.In an example, the FCoE PLOGI may include an SMAC address (e.g.,00:00:00:03:02:00), a DMAC address (e.g., 00:00:00:FF:FF:FC, apre-programmed WKA L2 cache entry), a SID (e.g., 03:02:00) and a DID(e.g., FF:FF:FC). The second converter 208 sends that FCoE PLOGI to theprotocol processing engine 204. In an embodiment, the Ethernet switchchip in the protocol processing engine 204 receives the FCoE PLOGI andprovides it to the CPU in the protocol processing engine 204.

The method 300 then proceeds to block 314 where the protocol processingengine sends an FCoE PLOGI ACC to the second converter. In anembodiment, the protocol processing engine 204 receives the FCoE PLOGIand, if the FCoE PLOGI is accepted, replies with an FCoE PLOGI ACC thatis sent to the second converter 208. In an embodiment, the CPU in theprotocol processing engine 204 determines whether the FCoE PLOGI isaccepted and, if so, sends an FCoE PLOGI ACC to the Ethernet switch chipin the protocol processing engine 204, which forwards the FCoE PLOGI ACCto the second converter 208. Processing actions to determine whether anFCoE PLOGI is accepted are known in the art and not discussed in furtherdetail here. In an example, an FCoE PLOGI ACC may include an SMACaddress (e.g., 00:00:00:FF:FF:FC), a DMAC address (e.g.,00:00:00:03:02:00), a SID (e.g. FF:FF:FC), and a DID (e.g., 03:02:00).

The method 300 then proceeds to block 316 where the second converterconverts the FCoE PLOGI ACC to an FC PLOGI ACC and provides the FC PLOGIACC to the target HBA in the storage IHS. In an embodiment, the secondconverter 208 receives the FCoE PLOGI ACC from the protocol processingengine 204 and provides it to the FCoE-to-FC engine 208 b, whichoperates to convert the FCoE PLOGI ACC to an FC PLOGI ACC by strippingthe FCoE header and trailer from the FCoE PLOGI ACC. In an example, theFC PLOGI ACC includes a SID (e.g., FF:FF:FC) and a DID (e.g., 03:02:00).The second converter 208 sends that FC PLOGI ACC through the second port212 a to the target HBA 216 a in the storage IHS 216.

The method 300 then proceeds to block 318 where the target HBA in thestorage IHS sends one or more FC name server registrations and/or FCname server queries to the switch IHS. In an embodiment, in response toreceiving the FC PLOGI ACC, the target HBA 216 a in the storage IHS 216generates and sends one or more FC name server registrations and/or FCname server queries that may include a Name Server WKA 0xFFFFFC to thesecond port 212 a on the switch IHS 202. In an example, the one or moreFC name server registrations and/or FC name server queries includes aSID (e.g., 03:02:00) and a DID (e.g., FF:FF:FC).

The method 300 then proceeds to block 320 where the second converterconverts the one or more FC name server registrations and/or FC nameserver queries to one or more FCoE name server registrations and/or FCoEname server queries and provides the one or more FCoE name serverregistrations and/or FCoE name server queries to the protocol processingengine. In an embodiment, the second converter 208 receives the one ormore FC name server registrations and/or FC name server queries throughthe second port 212 a and provides them to the FC-to-FCoE engine 208 a,which operates to convert the one or more FC name server registrationsand/or FC name server queries to one or more FCoE name serverregistrations and/or FCoE name server queries by wrapping the one ormore FC name server registrations and/or FC name server queries in anFCoE header and trailer. In an example, the one or more FCoE name serverregistrations and/or FCoE name server queries may include an SMACaddress (e.g., 00:00:00:03:02:00), a DMAC address (e.g.,00:00:00:FF:FF:FC), a SID (e.g., 03:02:00) and a DID (e.g., FF:FF:FC).The second converter 208 sends those one or more FCoE name serverregistrations and/or FCoE name server queries to the protocol processingengine 204. In an embodiment, the Ethernet switch chip in the protocolprocessing engine 204 receives the one or more FCoE name serverregistrations and/or FCoE name server queries and provides the one ormore FCoE name server registrations and/or FCoE name server queries tothe CPU in the protocol processing engine 204.

The method 300 then proceeds to block 322 where the protocol processingengine sends one or more FCoE name server registration accepts (ACCS)and/or FCoE name server query ACCS to the second converter. In anembodiment, the protocol processing engine 204 receives the one or moreFCoE name server registrations and/or FCoE name server queries and, ifthe one or more FCoE name server registrations and/or FCoE name serverqueries are accepted, replies with one or more FCoE name serverregistration ACCS and/or FCOE name server query ACCS that are sent tothe second converter 208. In an embodiment, the CPU in the protocolprocessing engine 204 determines whether the one or more FCoE nameserver registrations and/or FCoE name server queries are accepted and,if so, sends the one or more FCoE name server registration ACCS and/orFC name server query ACCS to the Ethernet switch chip in the protocolprocessing engine 204, which provides the one or more FCoE name serverregistration ACCS and/or FC name server query ACCS to the secondconverter 208. Processing actions to determine whether one or more FCoEname server registrations and/or FCoE name server queries are acceptedare known in the art and not discussed in further detail here.

The method 300 then proceeds to block 324 where the second converterconverts the one or more FCoE name server registration ACCS and/or FCoEname server query ACCS to one or more FC name server registration ACCSand/or FC name server query ACCS and provides the one or more FC nameserver registration ACCS and/or FC name server query ACCS to the targetHBA in the storage IHS. In an embodiment, the second converter 208receives the one or more FCoE name server registration ACCS and/or FCoEname server query ACCS from the protocol processing engine 204 andprovides it to the FCoE-to-FC engine 208 b, which operates to convertthe one or more FCoE name server registration ACCS and/or FCoE nameserver query ACCS to one or more FC name server registration ACCS and/orFC name server query ACCS by stripping the FCoE header and trailer fromthe one or more FCoE name server registration ACCS and/or FCoE nameserver query ACCS. The second converter 208 sends those one or more FCoEname server registration ACCS and/or FCoE name server query ACCS to thetarget HBA 216 a in the storage IHS 216. Following the target HBA 216 ain the storage IHS 216 receiving the one or more FCoE name serverregistration ACCS and/or FCoE name server query ACCS at block 324, thestorage IHS 216 and switch IHS 202 are set up for communication, and themethod 300 may proceed to method 500, discussed below, where the switchIHS 202 processes data traffic between the storage IHS 216 and theserver IHS 214, discussed below.

Referring now to FIG. 4, the method 400 for providing server/switchset-up is illustrated. In an embodiment, the method 400 may begin whenthe processing system of the switch IHS 202 first runs FC switch code ina software stack that is stored in the memory system of the switch IHS202 in response to, for example, connection, power up, or otherinitialization of the FC switching system 200. In some embodiments,during port initialization of the switch IHS 202 and prior to the method400, the first converter 206 is programmed (e.g., by programming the PHYchip) to perform a formatted conversion of native FC traffic (e.g., 8Gb/s FC traffic) into formatted FC over Ethernet (FCoE) traffic (e.g.,10GE FCoE frames). For example, the first converter 206 may beprogrammed to prepend a specific 3 byte FC-MAP (currently 00:00:00) toall incoming FC traffic FCID's, producing a specific 10GE frame offormat (currently 00:00:00:DD:AA:PP, where DD=domain (the first byte ofthe FCID), AA=area (the second byte of the FCID), and PP=port (the thirdbyte of the FCID, also referred to as the Arbitrated Loop PhysicalAddress (ALFA))) for both source and destination addresses.

In some embodiments, during switch initialization of the switch IHS 202and prior to the method 400, FCoE formatted FC Well Known Addresses(WKA's) are registered in the first converter 206 as Ethernet bridgingprotocol addresses, which operates to direct incoming FC Well KnownAddress (WKA) traffic that has been converted to the formatted FCoEtraffic to be sent to the Ethernet switch chip such that it may behandled using the FC switch code that is executable by the CPU. Inaddition, standard Ethernet bridging protocol addresses may bederegistered from the Ethernet switch chip. Furthermore, the Ethernetswitch chip may also be configured to not forward broadcast, multicast,or unknown unicast data traffic. As discussed in the method 400 below,the FC switch code in the CPU handles and generates protocol frames inthe specific FCoE format discussed herein.

The method 400 begins at block 402 where the initiator HBA in the serverIHS sends an FC fabric login (FLOGI) to the switch IHS. In anembodiment, the initiator HBA 214 a in the server IHS 214 generates andsends an FC FLOGI that may include the Login Server WKA 0xFFFFFE to thefirst port 210 a on the switch IHS 202. In an example, that FC FLOGI mayinclude a System Identification (SID) (e.g., 00:00:00, an unassigned FCidentification) and a Destination Identification (DID) (e.g., FF:FF:FE,the Login Server WKA).

The method 400 then proceeds to block 404 where the first converterconverts the FC FLOGI to an FCoE FLOGI and provides the FCoE FLOGI tothe protocol processing engine. In an embodiment, the first converter206 receives the FC FLOGI through the first port 210 a and provides itto the FC-to-FCoE engine 206 a, which operates to convert the FC FLOGIto an FCoE FLOGI by wrapping the FC FLOGI in an FCoE header and trailer.In an example, the FCoE FLOGI may include a source media access control(SMAC) address (e.g., 00:00:00:00:01:00), a destination MAC (DMAC)address (e.g., 00:00:00:FF:FF:FE, a pre-programmed layer 2 (L2) cacheentry), a SID (e.g., 00:00:00) and a DID (e.g., FF:FF:FE). The firstconverter 206 sends that FCoE FLOGI to the protocol processing engine204. In an embodiment, the Ethernet switch chip in the protocolprocessing engine 204 receives the FCoE FLOGI and provides it to the CPUin the protocol processing engine 204.

The method 400 then proceeds to block 406 where the protocol processingengine sends an FCoE FLOGI accept (ACC) to the first converter. In anembodiment, the protocol processing engine 204 receives the FCoE FLOGIand, if the FCoE FLOGI is accepted, replies with an FCoE FLOGI ACC thatis sent to the first converter 206. In an embodiment, the CPU I theprotocol processing engine 204 determines whether the FCoE FLOGI isaccepted and, if so, sends an FCoE FLOGI ACC to the Ethernet switch chipin the protocol processing engine 204, which forwards the FCoE FLOGI ACCto the first converter 206. Processing actions to determine whether anFCoE FLOGI is accepted are known in the art and not discussed in furtherdetail here. In an example, an FCoE FLOGI ACC may include an SMACaddress (e.g., 00:00:00:FF:FF:FE), a DMAC address (e.g.,00:00:00:03:01:00), a SID (e.g. FF:FF:FE), and a DID (e.g., 03:01:00).

The method 400 then proceeds to block 408 where the first converterconverts the FCoE FLOGI ACC to an FC FLOGI ACC and provides the FC FLOGIACC to the initator HBA in the server IHS. In an embodiment, the firstconverter 206 receives the FCoE FLOGI ACC from the protocol processingengine 204 and provides it to the FCoE-to-FC engine 206 b, whichoperates to convert the FCoE FLOGI ACC to an FC FLOGI ACC by strippingthe FCoE header and trailer from the FCoE FLOGI ACC. In an example, theFC FLOGI ACC includes a SID (e.g., FF:FF:FE) and a DID (e.g., 03:01:00).The first converter 206 sends that FC FLOGI ACC through the first port210 a to the initiator HBA 214 a in the server IHS 214.

The method 400 then proceeds to block 410 where the initiator HBA in theserver IHS sends an FC port login (PLOGI) to the switch IHS. In anembodiment, in response to receiving the FC FLOGI ACC, the initiator HBA214 a in the server IHS 214 generates and sends an FC PLOGI that mayinclude the Name Server WKA 0xFFFFFC to the first port 210 a on theswitch IHS 202. In an example, the FC PLOGI includes a SID (e.g.,03:01:00) and a DID (e.g., FF:FF:FC, the Name Server WKA).

The method 400 then proceeds to block 412 where the first converterconverts the FC PLOGI to an FCoE PLOGI and provides the FCoE PLOGI tothe protocol processing engine. In an embodiment, the first converter206 receives the FC PLOGI through the first port 210 a and provides itto the FC-to-FCoE engine 206 a, which operates to convert the FC PLOGIto an FCoE PLOGI by wrapping the FC PLOGI in an FCoE header and trailer.In an example, the FCoE PLOGI may include an SMAC address (e.g.,00:00:00:03:01:00), a DMAC address (e.g., 00:00:00:FF:FF:FC, apre-programmed WKA L2 cache entry), a SID (e.g., 03:01:00) and a DID(e.g., FF:FF:FC). The first converter 206 sends that FCoE PLOGI to theprotocol processing engine 204. In an embodiment, the Ethernet switchchip in the protocol processing engine 204 receives the FCoE PLOGI andprovides it to the CPU in the protocol processing engine 204.

The method 400 then proceeds to block 414 where the protocol processingengine sends an FCoE PLOGI ACC to the first converter. In an embodiment,the protocol processing engine 204 receives the FCoE PLOGI and, if theFCoE PLOGI is accepted, replies with an FCoE PLOGI ACC that is sent tothe first converter 206. In an embodiment, the CPU in the protocolprocessing engine 204 determines whether the FCoE PLOGI is accepted and,if so, sends an FCoE PLOGI ACC to the Ethernet switch chip in theprotocol processing engine 204, which forwards the FCoE PLOGI ACC to thefirst converter 206. Processing actions to determine whether an FCoEPLOGI is accepted are known in the art and not discussed in furtherdetail here. In an example, an FCoE PLOGI ACC may include an SMACaddress (e.g., 00:00:00:FF:FF:FC), a DMAC address (e.g.,00:00:00:03:01:00), a SID (e.g. FF:FF:FC), and a DID (e.g., 03:01:00).

The method 400 then proceeds to block 416 where the first converterconverts the FCoE PLOGI ACC to an FC PLOGI ACC and provides the FC PLOGIACC to the initator HBA in the server IHS. In an embodiment, the firstconverter 206 receives the FCoE PLOGI ACC from the protocol processingengine 204 and provides it to the FCoE-to-FC engine 206 b, whichoperates to convert the FCoE PLOGI ACC to an FC PLOGI ACC by strippingthe FCoE header and trailer from the FCoE PLOGI ACC. In an example, theFC PLOGI ACC includes a SID (e.g., FF:FF:FC) and a DID (e.g., 03:01:00).The first converter 206 sends that FC PLOGI ACC through the first port210 a to the initiator HBA 214 a in the server IHS 214.

The method 400 then proceeds to block 418 where the imitator HBA in theserver IHS sends one or more FC name server registrations and/or FC nameserver queries to the switch IHS. In an embodiment, in response toreceiving the FC PLOGI ACC, the initiator HBA 214 a in the server IHS214 generates and sends one or more FC name server registrations and/orFC name server queries that may include a Name Server WKA 0xFFFFFC tothe first port 210 a on the switch IHS 202. In an example, the one ormore FC name server registrations and/or FC name server queries includesa SID (e.g., 03:02:00) and a DID (e.g., FF:FF:FC).

The method 400 then proceeds to block 420 where the first converterconverts the one or more FC name server registrations and/or FC nameserver queries to one or more FCoE name server registrations and/or FCoEname server queries and provides the one or more FCoE name serverregistrations and/or FCoE name server queries to the protocol processingengine. In an embodiment, the first converter 206 receives the one ormore FC name server registrations and/or FC name server queries throughthe first port 210 a and provides them to the FC-to-FCoE engine 206 a,which operates to convert the one or more FC name server registrationsand/or FC name server queries to one or more FCoE name serverregistrations and/or FCoE name server queries by wrapping the one ormore FC name server registrations and/or FC name server queries in anFCoE header and trailer. In an example, the one or more FCoE name serverregistrations and/or FCoE name server queries may include an SMACaddress (e.g., 00:00:00:03:02:00), a DMAC address (e.g.,00:00:00:FF:FF:FC), a SID (e.g., 03:02:00) and a DID (e.g., FF:FF:FC).The first converter 206 sends those one or more FCoE name serverregistrations and/or FCoE name server queries to the protocol processingengine 204. In an embodiment, the Ethernet switch chip in the protocolprocessing engine 204 receives the one or more FCoE name serverregistrations and/or FCoE name server queries and provides the one ormore FCoE name server registrations and/or FCoE name server queries tothe CPU in the protocol processing engine 204.

The method 400 then proceeds to block 422 where the protocol processingengine sends one or more FCoE name server registration accepts (ACCS)and/or FCoE name server query ACCS to the first converter. In anembodiment, the protocol processing engine 204 receives the one or moreFCoE name server registrations and/or FCoE name server queries and, ifthe one or more FCoE name server registrations and/or FCoE name serverqueries are accepted, replies with one or more FCoE name serverregistration ACCS and/or FCOE name server query ACCS that are sent tothe first converter 206. In an embodiment, the CPU in the protocolprocessing engine 204 determines whether the one or more FCoE nameserver registrations and/or FCoE name server queries are accepted and,if so, sends the one or more FCoE name server registration ACCS and/orFC name server query ACCS to the Ethernet switch chip in the protocolprocessing engine 204, which provides the one or more FCoE name serverregistration ACCS and/or FC name server query ACCS to the firstconverter 206. Processing actions to determine whether one or more FCoEname server registrations and/or FCoE name server queries are acceptedare known in the art and not discussed in further detail here.

The method 400 then proceeds to block 424 where the first converterconverts the one or more FCoE name server registration ACCS and/or FCoEname server query ACCS to one or more FC name server registration ACCSand/or FC name server query ACCS and provides the one or more FC nameserver registration ACCS and/or FC name server query ACCS to theinitiator HBA in the server IHS. In an embodiment, the first converter206 receives the one or more FCoE name server registration ACCS and/orFCoE name server query ACCS from the protocol processing engine 204 andprovides it to the FCoE-to-FC engine 206 b, which operates to convertthe one or more FCoE name server registration ACCS and/or FCoE nameserver query ACCS to one or more FC name server registration ACCS and/orFC name server query ACCS by stripping the FCoE header and trailer fromthe one or more FCoE name server registration ACCS and/or FCoE nameserver query ACCS. The first converter 206 sends those one or more FCoEname server registration ACCS and/or FCoE name server query ACCS to theinitiator HBA 214 a in the server IHS 214.

The method 400 then proceeds to block 426 where the initiator HBA in theserver IHS sends an FC device PLOGI starting a SCSI conversation to theswitch IHS. In an embodiment, in response to receiving the one or moreFCoE name server registration ACCS and/or FCoE name server query ACCS,the initiator HBA 214 a in the server IHS 214 generates and sends FCdevice PLOGI starting a SCSI conversation to the first port 210 a on theswitch IHS 202. In an example, the FC device PLOGI starting a SCSIconversation includes a SID (e.g., 03:01:00) and a DID (e.g., 03:02:00).

The method 400 then proceeds to block 428 where the first converterconverts the FC device PLOGI to an FCoE device PLOGI and provides theFCoE device PLOGI to the protocol processing engine. In an embodiment,the first converter 206 receives the FC device PLOGI through the firstport 210 a and provides it to the FC-to-FCoE engine 206 a, whichoperates to convert the FC device PLOGI to an FCoE device PLOGI bywrapping the FC device PLOGI in an FCoE header and trailer. The firstconverter 206 sends the FCoE device PLOGI to the protocol processingengine 204. In an embodiment, the Ethernet switch chip in the protocolprocessing engine 204 receives the FCoE device PLOGI and provides theFCoE device PLOGI to the CPU in the protocol processing engine 204.

The method 400 then proceeds to block 430 where the protocol processingengine sends an FCoE device PLOGI accept (ACC) to the first converter.In an embodiment, the protocol processing engine 204 receives the FCoEdevice PLOGI and, if the FCoE device PLOGI is accepted, replies with anFCoE device PLOGI ACC that is sent to the first converter 206. In anembodiment, the CPU in the protocol processing engine 204 determineswhether the FCoE device PLOGI is accepted and, if so, sends the FCoEdevice PLOGI ACC to the Ethernet switch chip in the protocol processingengine 204, which provides the FCoE device PLOGI ACC to the firstconverter 206. Processing actions to determine whether an FCoE devicePLOGI is accepted are known in the art and not discussed in furtherdetail here.

The method 400 then proceeds to block 432 where the first converterconverts the FCoE device PLOGI ACC to an FC device PLOGI ACC andprovides the FC device PLOGI ACC to the initiator HBA in the server IHS.In an embodiment, the first converter 206 receives the FCoE device PLOGIACC from the protocol processing engine 204 and provides it to theFCoE-to-FC engine 206 b, which operates to convert the FCoE device PLOGIACC to an FC device PLOGI ACC by stripping the FCoE header and trailerfrom the FCoE device PLOGI ACC. The first converter 206 sends the FCdevice PLOGI ACC to the initiator HBA 214 a in the server IHS 214.Following the initiator HBA 214 a in the server IHS 214 receiving the FCdevice PLOGI ACC, the server IHS 214 and switch IHS 202 are set up forcommunication, and the method 400 may proceed to method 500, discussedbelow, where the switch IHS transmits data traffic between the serverIHS 214 and the storage IHS 216, discussed below. Following the methods300 and 400, the Ethernet L2 forwarding tables in the switch IHS 202 areprogrammed to provide direct server IHS 214/storage IHS 216 data planetraffic and communications with an SMAC address (e.g.,00:00:00:03:01:00), a SID (03:01:00), a DMAC address (e.g.,00:00:00:03:02:00), and a DID (03:02:00).

Referring now to FIG. 5, a method 500 for providing server/storagecommunication is illustrated that includes blocks 502 a, 504 a, 506 a,and 508 a that describe communications that initiate from the server IHS214 and that are provided by the switch IHS 202 to the storage IHS 216,and blocks 502 b, 504 b, 506 b, and 508 b that describe communicationsthat initiate from the storage IHS 216 and that are provided by theswitch IHS 202 to the server IHS 214. In these embodiments, the blocks502 a-508 a and 502 b-508 b are substantially similar and described inparallel, but one of skill in the art in possession of the presentdisclosure will recognize that some modifications to the blocks 502a-508 a or 502 b-508 b will fall within the scope of the presentdisclosure.

At block 502 a, the initiator HBA in the server IHS sends FC datatraffic to the switch IHS. In an embodiment, the initiator HBA 214 a inthe server IHS 214 may send FC data traffic to the first converter 206in the switch IHS 202 through the first port 210 a. Similarly, at block502 b, the target HBA in the storage IHS sends FC data traffic to theswitch IHS. In an embodiment, the target HBA 216 a in the storage IHS216 may send FC data traffic to the second converter 208 in the switchIHS 202 through the second port 212 a.

At block 504 a, the first converter converts the FC data traffic to FCoEdata traffic and sends the FCoE data traffic to the protocol processingengine. In an embodiment, the first converter 206 receives the FC datatraffic and provides it to the FC-to-FCoE engine 206 a, which convertsthe FC data traffic to FCoE data traffic by wrapping the FC data trafficin an FCoE header and trailer. The first converter 206 sends that FCoEdata traffic to the protocol processing engine 204. In an embodiment,the Ethernet switch chip in the protocol processing engine 204 receivesthe FCoE data traffic. Similarly, at block 504 b, the second converterconverts the FC data traffic to FCoE data traffic and sends the FCoEdata traffic to the protocol processing engine. In an embodiment, thesecond converter 208 receives the FC data traffic and provides it to theFC-to-FCoE engine 208 a, which converts the FC data traffic to FCoE datatraffic by wrapping the FC data traffic in an FCoE header and trailer.The second converter 208 sends that FCoE data traffic to the protocolprocessing engine 204. In an embodiment, the Ethernet switch chip in theprotocol processing engine 204 receives the FCoE data traffic.

At block 506 a, the protocol processing engine processes the FCoE datatraffic and sends it to the second converter. In an embodiment, theprotocol processing engine 204 processes the FCoE data traffic andforwards the processed FCoE data traffic to the second converter 208. Inan embodiment, the Ethernet switch chip in the protocol processingengine 204 processes the FCoE data traffic using the forwarding tables,and forwards it to the second converter 208. Similarly, at block 506 b,the protocol processing engine processes the FCoE data traffic and sendsit to the first converter. In an embodiment, the protocol processingengine 204 processes the FCoE data traffic and forwards the processedFCoE data traffic to the first converter 206. In an embodiment, theEthernet switch chip in the protocol processing engine 204 processes theFCoE data traffic using the forwarding tables, and forwards it to thesecond converter 208. The actions performed by the Ethernet switch chipin the protocol processing engine 204 in processing and forwarding theFCoE data traffic may include MAC address-based forwarding actions knownin the art.

At block 508 a, the second converter converts the FCoE data traffic toFC data traffic and sends the FC data traffic to the target HBA in thestorage IHS. In an embodiment, the second converter 208 receives theFCoE data traffic and provides it to the FCoE-to-FC engine 208 b, whichconverts the FCoE data traffic to FC data traffic by stripping the FCoEheader and trailer from the FCoE data traffic. The second converter 208then sends the FC data traffic through second port 212 a to the targetHBA 216 a in the storage IHS 216. Similarly, at block 508 b, the firstconverter converts the FCoE data traffic to FC data traffic and sendsthe FC data traffic to the initiator HBA in the server IHS. In anembodiment, the first converter 206 receives the FCoE data traffic andprovides it to the FCoE-to-FC engine 206 b, which converts the FCoE datatraffic to FC data traffic by stripping the FCoE header and trailer fromthe FCoE data traffic. The first converter 206 then sends the FC datatraffic through first port 210 a to the initiator HBA 214 a in theserver IHS 214.

Thus, systems and methods have been described that provide a FibreChannel switching system that allows Fibre Channel communicationsbetween IHSs via a switch IHS that includes programmed PHY chips thatperform FC to FCoE (and FCoE to FC) protocol conversions such that anEthernet switch chip may be utilized to make switching decisions usingFCoE headers and Ethernet L2 forwarding tables. These systems andmethods provide for the manufacture and use of switch IHSs in FC SANsystems that are inexpensive relative to conventional FC switches,reducing the current barriers to entry into the FC switch market, andopening up the use of FC fabric technology to more users.

Although illustrative embodiments have been shown and described, a widerange of modification, change and substitution is contemplated in theforegoing disclosure and in some instances, some features of theembodiments may be employed without a corresponding use of otherfeatures. Accordingly, it is appropriate that the appended claims beconstrued broadly and in a manner consistent with the scope of theembodiments disclosed herein.

What is claimed is:
 1. A Fibre Channel (FC) switch system, comprising: afirst converter that is coupled to a first port and that is configuredto receive first FC data traffic from an initiator system through thefirst port and convert the first FC data traffic to first FC overEthernet (FCoE) data traffic; a protocol processing engine that iscoupled to the first converter and that is configured to receive thefirst FCoE data traffic from the first converter and process the firstFCoE data traffic to provide second FCoE data traffic for delivery to atarget system; and a second converter that is coupled to the protocolprocessing engine and a second port, wherein the second converter isconfigured to receive the second FCoE data traffic from the protocolprocessing engine, convert the second FCoE data traffic to second FCdata traffic, and send the second FC data traffic through the secondport to the target system.
 2. The system of claim 1, wherein theconversion of the first FC data traffic to the first FCoE data trafficby the first converter includes generating an FCoE source address forthe initiator system from an FC source address for the initiator systemthat is included in the first FC data traffic.
 3. The system of claim 1,wherein the conversion of the first FC data traffic to the first FCoEdata traffic by the first converter includes generating an FCoEdestination address for the target system from an FC destination addressfor the target system that is included in the first FC data traffic. 4.The system of claim 1, wherein FCoE formatted FC Well Known Addresses(WKA's) are registered in the first converter as Ethernet bridgingprotocol addresses.
 5. The system of claim 1, wherein the protocolprocessing engine includes an Ethernet switch chip that is configured toprocess the first FCoE data traffic to provide the second FCoE datatraffic for delivery to the target system.
 6. The system of claim 5,wherein standard Ethernet bridging protocol addresses are deregisteredfrom the Ethernet switch chip.
 7. The system of claim 5, the Ethernetswitch chip is configured such that broadcast data traffic, multicastdata traffic, and unknown unicast data traffic are not forwarded.
 8. Aninformation handling system (IHS) network, comprising: a server IHS thatis configured to communicate using a Fibre Channel (FC) protocol; astorage IHS that is configured to communicate using the FC protocol; anda switch IHS coupled to the server IHS and the storage IHS, wherein theswitch includes: a first converter that is configured to receive firstFC data traffic from the server IHS and convert the first FC datatraffic to first FC over Ethernet (FCoE) data traffic; a protocolprocessing engine that is coupled to the first converter and that isconfigured to receive the first FCoE data traffic from the firstconverter and process the first FCoE data traffic to provide second FCoEdata traffic for delivery to the storage IHS; and a second converterthat is coupled to the protocol processing engine and the storage IHS,wherein the second converter is configured to receive the second FCoEdata traffic from the protocol processing engine, convert the secondFCoE data traffic to second FC data traffic, and send the second FC datatraffic to the storage IHS.
 9. The IHS of claim 8, wherein theconversion of the first FC data traffic to the first FCoE data trafficby the first converter includes generating an FCoE source address forthe server IHS from an FC source address for the server IHS that isincluded in the first FC data traffic.
 10. The IHS of claim 8, whereinthe conversion of the first FC data traffic to the first FCoE datatraffic by the first converter includes generating an FCoE destinationaddress for the storage IHS from an FC destination address for thestorage IHS that is included in the first FC data traffic.
 11. The IHSof claim 8, wherein FCoE formatted FC Well Known Addresses (WKA's) areregistered in the first converter as Ethernet bridging protocoladdresses.
 12. The IHS of claim 8, wherein the protocol processingengine includes an Ethernet switch chip that is configured to processthe first FCoE data traffic to provide the second FCoE data traffic fordelivery to the storage IHS.
 13. The IHS of claim 12, wherein standardEthernet bridging protocol addresses are deregistered from the Ethernetswitch chip.
 14. The IHS of claim 12, wherein the Ethernet switch chipis configured such that broadcast data traffic, multicast data traffic,and unknown unicast data traffic are not forwarded.
 15. A method fortransmitting Fibre Channel (FC) data traffic, comprising: receiving, bya first converter, first FC data traffic from a server IHS; converting,by the first converter, the first FC data traffic to first FC overEthernet (FCoE) data traffic; receiving, by a protocol processing enginefrom the first converter, the first FCoE data traffic; processing, bythe protocol processing engine, the first FCoE data traffic to providesecond FCoE data traffic for delivery to a storage IHS; receiving, by asecond converter from the protocol processing engine, the second FCoEdata traffic; converting, by the second converter, the second FCoE datatraffic to second FC data traffic; and sending, by the second converter,the second FC data traffic to the storage IHS
 16. The method of claim15, wherein the conversion of the first FC data traffic to the firstFCoE data traffic by the first converter includes generating an FCoEsource address for the server IHS from an FC source address for theserver IHS that is included in the first FC data traffic.
 17. The methodof claim 15, wherein the conversion of the first FC data traffic to thefirst FCoE data traffic by the first converter includes generating anFCoE destination address for the storage IHS from an FC destinationaddress for the storage IHS that is included in the first FC datatraffic.
 18. The method of claim 15, wherein FCoE formatted FC WellKnown Addresses (WKA's) are registered in the first converter asEthernet bridging protocol addresses.
 19. The method of claim 15,wherein the protocol processing engine includes an Ethernet switch chipthat is configured to process the first FCoE data traffic to provide thesecond FCoE data traffic for delivery to the storage IHS.
 20. The methodof claim 20, wherein the Ethernet switch chip is configured such thatbroadcast data traffic, multicast data traffic, and unknown unicast datatraffic are not forwarded.